Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Serialization Refactor #30

Merged
merged 11 commits into from
Jun 1, 2020
Merged

Serialization Refactor #30

merged 11 commits into from
Jun 1, 2020

Conversation

Karsten1987
Copy link
Collaborator

@Karsten1987 Karsten1987 commented May 21, 2020

  • C++ Typesupport serialization and tests
  • C Typesupport serialization, C Message Fixtures and tests

Signed-off-by: Knese Karsten <karsten.knese@us.bosch.com>
Signed-off-by: Knese Karsten <karsten.knese@us.bosch.com>
Signed-off-by: Knese Karsten <karsten.knese@us.bosch.com>
Signed-off-by: Knese Karsten <karsten.knese@us.bosch.com>
Signed-off-by: Knese Karsten <karsten.knese@us.bosch.com>
Signed-off-by: Knese Karsten <karsten.knese@us.bosch.com>
Signed-off-by: Knese Karsten <karsten.knese@us.bosch.com>
Signed-off-by: Knese Karsten <karsten.knese@us.bosch.com>
Signed-off-by: Knese Karsten <karsten.knese@us.bosch.com>
@Karsten1987 Karsten1987 marked this pull request as ready for review May 23, 2020 19:37
Signed-off-by: Knese Karsten <karsten.knese@us.bosch.com>
@Karsten1987
Copy link
Collaborator Author

There's still a reported memory corruption when running WStrings in C++.
Further, I need to enhance the message fixtures with a real copy constructor in order to work with multinested types in C.

Both which could be addressed in a follow up PR.

Signed-off-by: Knese Karsten <karsten.knese@us.bosch.com>
@Karsten1987 Karsten1987 merged commit c5ef31a into master Jun 1, 2020
@delete-merged-branch delete-merged-branch bot deleted the serialization_refactor branch June 1, 2020 21:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants